Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 9b9adc69b37c2d8d7c08b44da132ffca309ac0b3537c708748816f82ae17d90c

Tx prefix hash: 6914ea1a3c95cce1270417a710cd1503f9aab962b84a41091db165f4fece3222
Tx public key: 93a5197d813e40007e31786c545eb4d9747d759fe1e414c99f0d637af4e0e733
Timestamp: 1578242932 Timestamp [UCT]: 2020-01-05 16:48:52 Age [y:d:h:m:s]: 04:363:00:17:20
Block: 39326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148686 RingCT/type: yes/0
Extra: 0193a5197d813e40007e31786c545eb4d9747d759fe1e414c99f0d637af4e0e73302110000007bb221b3d1000000000000000000

1 output(s) for total of 454.671241703000 dcy

stealth address amount amount idx
00: 3bed1e87672d11c3774b009bf5830d273b16856ef20eb136443dfb4d20556bcc 454.671241703000 67738 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 39336, "vin": [ { "gen": { "height": 39326 } } ], "vout": [ { "amount": 454671241703, "target": { "key": "3bed1e87672d11c3774b009bf5830d273b16856ef20eb136443dfb4d20556bcc" } } ], "extra": [ 1, 147, 165, 25, 125, 129, 62, 64, 0, 126, 49, 120, 108, 84, 94, 180, 217, 116, 125, 117, 159, 225, 228, 20, 201, 159, 13, 99, 122, 244, 224, 231, 51, 2, 17, 0, 0, 0, 123, 178, 33, 179, 209, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8