Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b0544f00f5839fdc754805adde74820f9693a4188b078d9fc6e43e22f3dfd59

Tx prefix hash: 0e369a31458dd55a896a77385f76488009c15df5f0ddacae708e9ff045731509
Tx public key: ac8b4ee62b1ea38236cd5755c1da44dff11f4f3709a325a8c2fc3850012b9128
Timestamp: 1702218672 Timestamp [UCT]: 2023-12-10 14:31:12 Age [y:d:h:m:s]: 01:346:04:23:38
Block: 910136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506291 RingCT/type: yes/0
Extra: 01ac8b4ee62b1ea38236cd5755c1da44dff11f4f3709a325a8c2fc3850012b9128021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fc907d91e1a64c1b190ded8aee707bb84c418c561cab202228dd884f2f4de2f 0.600000000000 1367281 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": 910146, "vin": [ { "gen": { "height": 910136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fc907d91e1a64c1b190ded8aee707bb84c418c561cab202228dd884f2f4de2f" } } ], "extra": [ 1, 172, 139, 78, 230, 43, 30, 163, 130, 54, 205, 87, 85, 193, 218, 68, 223, 241, 31, 79, 55, 9, 163, 37, 168, 194, 252, 56, 80, 1, 43, 145, 40, 2, 17, 0, 0, 0, 7, 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