Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13aa9fdd1a6adcfd589ac3b6ff74147f43ead1e46c6940d7f36e7d74d50c98df

Tx prefix hash: 4358c8f5aaeea9fecca0bc3fe8e86837f3a51f30d0362950658959e610599e68
Tx public key: 45c429c80435e909ef2963e97bc4b06af11fe64d0690aa967eda548c5ba1cef8
Timestamp: 1577672016 Timestamp [UCT]: 2019-12-30 02:13:36 Age [y:d:h:m:s]: 05:004:18:27:48
Block: 34706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1153405 RingCT/type: yes/0
Extra: 0145c429c80435e909ef2963e97bc4b06af11fe64d0690aa967eda548c5ba1cef802110000000a4943cd9f000000000000000000

1 output(s) for total of 470.983258725000 dcy

stealth address amount amount idx
00: 833822e0ad06fc9b96435b71c994a9bcaed66d6d9386fe7f5fb7966a211a50f5 470.983258725000 58450 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": 34716, "vin": [ { "gen": { "height": 34706 } } ], "vout": [ { "amount": 470983258725, "target": { "key": "833822e0ad06fc9b96435b71c994a9bcaed66d6d9386fe7f5fb7966a211a50f5" } } ], "extra": [ 1, 69, 196, 41, 200, 4, 53, 233, 9, 239, 41, 99, 233, 123, 196, 176, 106, 241, 31, 230, 77, 6, 144, 170, 150, 126, 218, 84, 140, 91, 161, 206, 248, 2, 17, 0, 0, 0, 10, 73, 67, 205, 159, 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