Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ddb695a1b98919b8f44e7f52d08c3be574f1ce7316c17e42f835993489e5902

Tx prefix hash: bdf9af77cfca79c866acd0d294e42f1eae406fa8fba3832167bcebc065fc05c3
Tx public key: 3143b8b9ce768b3ea58a6c7769a295479cbf4d01dde7e471c20d4d0bf76841c4
Timestamp: 1706473870 Timestamp [UCT]: 2024-01-28 20:31:10 Age [y:d:h:m:s]: 01:009:07:42:19
Block: 945392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267716 RingCT/type: yes/0
Extra: 013143b8b9ce768b3ea58a6c7769a295479cbf4d01dde7e471c20d4d0bf76841c402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67f361730a813cea17f184500119d375ab2133ce82d13d2dcb06f1d5a0c66ee6 0.600000000000 1403704 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": 945402, "vin": [ { "gen": { "height": 945392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67f361730a813cea17f184500119d375ab2133ce82d13d2dcb06f1d5a0c66ee6" } } ], "extra": [ 1, 49, 67, 184, 185, 206, 118, 139, 62, 165, 138, 108, 119, 105, 162, 149, 71, 156, 191, 77, 1, 221, 231, 228, 113, 194, 13, 77, 11, 247, 104, 65, 196, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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