Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97f5eb630d07e4ed5d8638e22e280d8960598d4de0f1045b76479fe406280c14

Tx prefix hash: 12622fff7de59e1f520c72a042c85b685880e0a8b0c3dbdf98493fc40a5e0527
Tx public key: b2fa6a560c9e4bd8f8e822e6249d8f6295afdaa673730a354090da9fc84a40b4
Timestamp: 1710507288 Timestamp [UCT]: 2024-03-15 12:54:48 Age [y:d:h:m:s]: 00:345:18:49:55
Block: 978882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247192 RingCT/type: yes/0
Extra: 01b2fa6a560c9e4bd8f8e822e6249d8f6295afdaa673730a354090da9fc84a40b402110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6da0c4e4116d9fbd85438ad8bf83cde9926bd1a506034b6517c458ec4cc39640 0.600000000000 1438911 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": 978892, "vin": [ { "gen": { "height": 978882 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6da0c4e4116d9fbd85438ad8bf83cde9926bd1a506034b6517c458ec4cc39640" } } ], "extra": [ 1, 178, 250, 106, 86, 12, 158, 75, 216, 248, 232, 34, 230, 36, 157, 143, 98, 149, 175, 218, 166, 115, 115, 10, 53, 64, 144, 218, 159, 200, 74, 64, 180, 2, 17, 0, 0, 0, 4, 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