Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be4d5702f4b56bd441832428c2ebf3a8d107a834912ab3c7eef98e8bdc94e661

Tx prefix hash: 1940fdb4c5eb45ba1ee593c28b8ac95b060b254fb49836ddf3a992dbf2abb1ff
Tx public key: 466973db6532f1f1be5671205b8536b3c24f4c8e29bb0df055d3c0bcc012a50f
Timestamp: 1728162253 Timestamp [UCT]: 2024-10-05 21:04:13 Age [y:d:h:m:s]: 00:184:21:25:46
Block: 1125228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131930 RingCT/type: yes/0
Extra: 01466973db6532f1f1be5671205b8536b3c24f4c8e29bb0df055d3c0bcc012a50f02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b7a2628f2736286131eca6d7eed58ff15cd4661efd8a3fcf37ca3f191a59bb2 0.600000000000 1607905 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": 1125238, "vin": [ { "gen": { "height": 1125228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b7a2628f2736286131eca6d7eed58ff15cd4661efd8a3fcf37ca3f191a59bb2" } } ], "extra": [ 1, 70, 105, 115, 219, 101, 50, 241, 241, 190, 86, 113, 32, 91, 133, 54, 179, 194, 79, 76, 142, 41, 187, 13, 240, 85, 211, 192, 188, 192, 18, 165, 15, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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