Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eaab92c90c28885dda151d1ac93e4e75b858d3720ec1f04e9914d53840bebb2f

Tx prefix hash: 690d26f1375206919495b77b575e7ae1fa5d9760a9ce7fbb00014f9a2d2bdd72
Tx public key: 36a25d800bfa5b09f49836a3f1a1fdf5c317620984bf3a30bc205734f13a19a9
Timestamp: 1734450652 Timestamp [UCT]: 2024-12-17 15:50:52 Age [y:d:h:m:s]: 00:101:21:10:15
Block: 1177269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72577 RingCT/type: yes/0
Extra: 0136a25d800bfa5b09f49836a3f1a1fdf5c317620984bf3a30bc205734f13a19a9021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b00b62f9f1b42c0dc6ab3845fb1dd35667a822f33244e649b0cccde8f41c8fa 0.600000000000 1663636 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": 1177279, "vin": [ { "gen": { "height": 1177269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b00b62f9f1b42c0dc6ab3845fb1dd35667a822f33244e649b0cccde8f41c8fa" } } ], "extra": [ 1, 54, 162, 93, 128, 11, 250, 91, 9, 244, 152, 54, 163, 241, 161, 253, 245, 195, 23, 98, 9, 132, 191, 58, 48, 188, 32, 87, 52, 241, 58, 25, 169, 2, 17, 0, 0, 0, 6, 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