Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30ee5f853c2158797dc7867fa8d132de25f1e4ebdf5ce658872d1c8e449f246c

Tx prefix hash: aba60b5e0150be410082c1060ce71afe22854c271286627f226bad1a07e743ba
Tx public key: f722b58e9b8f5838ff76f7c8ebf6e6608c309fbf1607e890ea3a738ab9e172f1
Timestamp: 1734673789 Timestamp [UCT]: 2024-12-20 05:49:49 Age [y:d:h:m:s]: 00:093:21:12:28
Block: 1179120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66844 RingCT/type: yes/0
Extra: 01f722b58e9b8f5838ff76f7c8ebf6e6608c309fbf1607e890ea3a738ab9e172f1021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb2ad100ed12d65bd9b6a68e1093e85fe5aa1bd4ec1d3662f6baed0277c5c77f 0.600000000000 1665511 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": 1179130, "vin": [ { "gen": { "height": 1179120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb2ad100ed12d65bd9b6a68e1093e85fe5aa1bd4ec1d3662f6baed0277c5c77f" } } ], "extra": [ 1, 247, 34, 181, 142, 155, 143, 88, 56, 255, 118, 247, 200, 235, 246, 230, 96, 140, 48, 159, 191, 22, 7, 232, 144, 234, 58, 115, 138, 185, 225, 114, 241, 2, 17, 0, 0, 0, 1, 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