Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 349d02b4c209da915e1ba437283196c727d354a33284f64e6242427c72e952b1

Tx prefix hash: 48ba8d1b29dd0dd850c60134641819025a7074a92643b9e2cc2cd10e6b65b567
Tx public key: 84ad84cf2d9f086b4a1049d84717931797fc64517c2d37fe4ac6e9c92d875bdf
Timestamp: 1751070215 Timestamp [UCT]: 2025-06-28 00:23:35 Age [y:d:h:m:s]: 00:145:18:34:05
Block: 1314157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102273 RingCT/type: yes/0
Extra: 0184ad84cf2d9f086b4a1049d84717931797fc64517c2d37fe4ac6e9c92d875bdf0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31bccea5d08d1635608c7fbae02f87bbb15476f6bcb67d6b55d7b0195b725756 0.600000000000 1801802 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": 1314167, "vin": [ { "gen": { "height": 1314157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31bccea5d08d1635608c7fbae02f87bbb15476f6bcb67d6b55d7b0195b725756" } } ], "extra": [ 1, 132, 173, 132, 207, 45, 159, 8, 107, 74, 16, 73, 216, 71, 23, 147, 23, 151, 252, 100, 81, 124, 45, 55, 254, 74, 198, 233, 201, 45, 135, 91, 223, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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