Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d701591887791c7db35ff5ab1723246d48598d4eb7c8dfeea61bcbf8ba316de6

Tx prefix hash: acca83843d208c13a411571f7f6af1df6c66e777e1ac8ae87be02c9a533c9259
Tx public key: b22bce62f2aa1517b7c6cd7c2b9551f81583b7041f2e3989a04929a70657036f
Timestamp: 1731598793 Timestamp [UCT]: 2024-11-14 15:39:53 Age [y:d:h:m:s]: 00:127:09:33:27
Block: 1153629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90866 RingCT/type: yes/0
Extra: 01b22bce62f2aa1517b7c6cd7c2b9551f81583b7041f2e3989a04929a70657036f021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2b59572fef27c84d88915a9f99ca37950ab112452b5fefe979d44c485d29b9a 0.600000000000 1639238 of 15

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": 1153639, "vin": [ { "gen": { "height": 1153629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2b59572fef27c84d88915a9f99ca37950ab112452b5fefe979d44c485d29b9a" } } ], "extra": [ 1, 178, 43, 206, 98, 242, 170, 21, 23, 183, 198, 205, 124, 43, 149, 81, 248, 21, 131, 183, 4, 31, 46, 57, 137, 160, 73, 41, 167, 6, 87, 3, 111, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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