Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0245dc5bdd61136205b62f1eed682ef74ccab429a76485367f200945e6e0a141

Tx prefix hash: 11f88614e11aa32e9eecc3700f1ca0a4008f031524dbd2d6c163dade4d16ad46
Tx public key: 06ac8e5d8b1e73f73258e599363973019c39cd1baf6a1a2acf8bcdac169a5ea9
Timestamp: 1702349566 Timestamp [UCT]: 2023-12-12 02:52:46 Age [y:d:h:m:s]: 01:333:04:40:24
Block: 911229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496987 RingCT/type: yes/0
Extra: 0106ac8e5d8b1e73f73258e599363973019c39cd1baf6a1a2acf8bcdac169a5ea9021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10769ee1462bfcb4a7f9d0d46e75af3a33f8dab9999ddf6d68cc353a58d91428 0.600000000000 1368410 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": 911239, "vin": [ { "gen": { "height": 911229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10769ee1462bfcb4a7f9d0d46e75af3a33f8dab9999ddf6d68cc353a58d91428" } } ], "extra": [ 1, 6, 172, 142, 93, 139, 30, 115, 247, 50, 88, 229, 153, 54, 57, 115, 1, 156, 57, 205, 27, 175, 106, 26, 42, 207, 139, 205, 172, 22, 154, 94, 169, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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