Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdc88d2963d49206daf5929a481aefe14f8652d212e57b747f3ae7124b54d0a1

Tx prefix hash: bd35c2025a836ee70bb79eeedc7d27fd816f4d318adc69e3fa0bfafb896a64a3
Tx public key: b88b7f8fe049e8f32aeba2ff7930518c2530ad299dbd8b8b9c243b4d46e2a96c
Timestamp: 1716478432 Timestamp [UCT]: 2024-05-23 15:33:52 Age [y:d:h:m:s]: 01:166:13:42:02
Block: 1028360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377628 RingCT/type: yes/0
Extra: 01b88b7f8fe049e8f32aeba2ff7930518c2530ad299dbd8b8b9c243b4d46e2a96c0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 908deb77648007ce2b30e35d42fe73e9c6d80803682becf1c4c1353abeda085c 0.600000000000 1496351 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": 1028370, "vin": [ { "gen": { "height": 1028360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "908deb77648007ce2b30e35d42fe73e9c6d80803682becf1c4c1353abeda085c" } } ], "extra": [ 1, 184, 139, 127, 143, 224, 73, 232, 243, 42, 235, 162, 255, 121, 48, 81, 140, 37, 48, 173, 41, 157, 189, 139, 139, 156, 36, 59, 77, 70, 226, 169, 108, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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