Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72a36a897900859a61744f969a8dc41cf3e6b8ddb36d6ceb145fe9810353ed89

Tx prefix hash: 8b424039e602b6ab3493a1ad93d56bd2d8ad9d7fd6b44f77c673ab7c52beccb7
Tx public key: 456e636a794989a11d0714f6b0031aa0da1e0b73461dbe502b84963315a4ac94
Timestamp: 1574107107 Timestamp [UCT]: 2019-11-18 19:58:27 Age [y:d:h:m:s]: 05:009:12:50:16
Block: 12124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1149885 RingCT/type: yes/0
Extra: 01456e636a794989a11d0714f6b0031aa0da1e0b73461dbe502b84963315a4ac9402110000000166a80d00000000000000000000

1 output(s) for total of 559.537300763000 dcy

stealth address amount amount idx
00: e1de832b7d27aa383feb9afbcdfcc46c1466bbda13bb64a2e3ff3ef93baf8d6a 559.537300763000 13211 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": 12134, "vin": [ { "gen": { "height": 12124 } } ], "vout": [ { "amount": 559537300763, "target": { "key": "e1de832b7d27aa383feb9afbcdfcc46c1466bbda13bb64a2e3ff3ef93baf8d6a" } } ], "extra": [ 1, 69, 110, 99, 106, 121, 73, 137, 161, 29, 7, 20, 246, 176, 3, 26, 160, 218, 30, 11, 115, 70, 29, 190, 80, 43, 132, 150, 51, 21, 164, 172, 148, 2, 17, 0, 0, 0, 1, 102, 168, 13, 0, 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