Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc0dffd529a41a814948ffda8e15b100a29e9145737c7acfd6a6499d13c6c98b

Tx prefix hash: bb3a9d607c7b7d8aa3eea8be88ac155feedb0e3142a4ae221d077b2e007e98a9
Tx public key: 3420813590db56cefebb2cc1fd6876a90aa603c570b91215fe1e1b72e6e0d7b1
Timestamp: 1723061881 Timestamp [UCT]: 2024-08-07 20:18:01 Age [y:d:h:m:s]: 00:199:07:35:57
Block: 1082940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142300 RingCT/type: yes/0
Extra: 013420813590db56cefebb2cc1fd6876a90aa603c570b91215fe1e1b72e6e0d7b102110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2dd6f8746972642ec0396dc9a0daa9bb06660cbf4db1ff9653f7798b2363f4ea 0.600000000000 1556775 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": 1082950, "vin": [ { "gen": { "height": 1082940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2dd6f8746972642ec0396dc9a0daa9bb06660cbf4db1ff9653f7798b2363f4ea" } } ], "extra": [ 1, 52, 32, 129, 53, 144, 219, 86, 206, 254, 187, 44, 193, 253, 104, 118, 169, 10, 166, 3, 197, 112, 185, 18, 21, 254, 30, 27, 114, 230, 224, 215, 177, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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