Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7af4e3e2216cae01c7df98b74a84870a2ddbec308b81e64af522272d42697061

Tx prefix hash: af17a37207ba99c5cfb9fcd6b0fb4810cab3f8a77521264f095b099e8e1bb425
Tx public key: 83a0b5a555959b5d76820b40d0a15c79e3d7b82a70fa95391888ed08a351fc13
Timestamp: 1673215485 Timestamp [UCT]: 2023-01-08 22:04:45 Age [y:d:h:m:s]: 02:070:13:32:46
Block: 670542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 572132 RingCT/type: yes/0
Extra: 0183a0b5a555959b5d76820b40d0a15c79e3d7b82a70fa95391888ed08a351fc1302110000000452542ceb000000000000000000

1 output(s) for total of 3.683120732000 dcy

stealth address amount amount idx
00: b70fb8ced3cf5eea3638c33f3af0f433acdf09788040b594638c819b3f7c04a5 3.683120732000 1111953 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": 670552, "vin": [ { "gen": { "height": 670542 } } ], "vout": [ { "amount": 3683120732, "target": { "key": "b70fb8ced3cf5eea3638c33f3af0f433acdf09788040b594638c819b3f7c04a5" } } ], "extra": [ 1, 131, 160, 181, 165, 85, 149, 155, 93, 118, 130, 11, 64, 208, 161, 92, 121, 227, 215, 184, 42, 112, 250, 149, 57, 24, 136, 237, 8, 163, 81, 252, 19, 2, 17, 0, 0, 0, 4, 82, 84, 44, 235, 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