Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71fd4735f76831286c335f8316cb1bb6ad5ed0255e58d3e967e775f6a20c9db4

Tx prefix hash: 3d08c94b18085f9a346d412951557b71116b41e18123371097095726e4f1e4d4
Tx public key: 8e00933a31ebad1f59bc3d068e70a1be9b7d8fdcecb8b607ea5997443784a964
Timestamp: 1703904669 Timestamp [UCT]: 2023-12-30 02:51:09 Age [y:d:h:m:s]: 01:102:00:01:53
Block: 924111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334021 RingCT/type: yes/0
Extra: 018e00933a31ebad1f59bc3d068e70a1be9b7d8fdcecb8b607ea5997443784a9640211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d88907ee0f211be9344250d697375632d0f23f4c87a42028650e5ac75bd8d48a 0.600000000000 1381855 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": 924121, "vin": [ { "gen": { "height": 924111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d88907ee0f211be9344250d697375632d0f23f4c87a42028650e5ac75bd8d48a" } } ], "extra": [ 1, 142, 0, 147, 58, 49, 235, 173, 31, 89, 188, 61, 6, 142, 112, 161, 190, 155, 125, 143, 220, 236, 184, 182, 7, 234, 89, 151, 68, 55, 132, 169, 100, 2, 17, 0, 0, 0, 2, 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