Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3631dd90e5b1cbce99cde1a8dbdd1bf8a77db403ba8bef1db38082c7aac5bffc

Tx prefix hash: 435d0b2b42f978e95f66abaa638835f974aee3bfee11b0a6668e477678a3f650
Tx public key: 03a8df690e354bafd8057367adae8018fbaa80f223279f88624cf69489667cba
Timestamp: 1713039733 Timestamp [UCT]: 2024-04-13 20:22:13 Age [y:d:h:m:s]: 00:265:03:40:21
Block: 999828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189825 RingCT/type: yes/0
Extra: 0103a8df690e354bafd8057367adae8018fbaa80f223279f88624cf69489667cba0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: 3aaaf23dbc4e3a60bbd758f128f32d0ed4eafd7c7d751e2e56c53bcca0d16f00 0.600010000000 1460314 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": 999838, "vin": [ { "gen": { "height": 999828 } } ], "vout": [ { "amount": 600010000, "target": { "key": "3aaaf23dbc4e3a60bbd758f128f32d0ed4eafd7c7d751e2e56c53bcca0d16f00" } } ], "extra": [ 1, 3, 168, 223, 105, 14, 53, 75, 175, 216, 5, 115, 103, 173, 174, 128, 24, 251, 170, 128, 242, 35, 39, 159, 136, 98, 76, 246, 148, 137, 102, 124, 186, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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