Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff50a010b47894933d9c68a5e815e3623420afc3f4ee3c36dc449fd3175c0dce

Tx prefix hash: cfc752f0dd223e1d670ab7909c75883c9bd6f2b96b0e60824840f88375f6b0d6
Tx public key: bd36103a4f21bd1cbb8bdedf04dd6eee1c488dc1c7e2cd1eb3e041dca2c70f4e
Timestamp: 1703267679 Timestamp [UCT]: 2023-12-22 17:54:39 Age [y:d:h:m:s]: 01:332:20:19:33
Block: 918838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496733 RingCT/type: yes/0
Extra: 01bd36103a4f21bd1cbb8bdedf04dd6eee1c488dc1c7e2cd1eb3e041dca2c70f4e0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87009cab9297c09895c80ff94327edb39e1ef0811c25ee4dbe526265e5c0c4b9 0.600000000000 1376502 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": 918848, "vin": [ { "gen": { "height": 918838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87009cab9297c09895c80ff94327edb39e1ef0811c25ee4dbe526265e5c0c4b9" } } ], "extra": [ 1, 189, 54, 16, 58, 79, 33, 189, 28, 187, 139, 222, 223, 4, 221, 110, 238, 28, 72, 141, 193, 199, 226, 205, 30, 179, 224, 65, 220, 162, 199, 15, 78, 2, 17, 0, 0, 0, 7, 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