Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdf3e503659693813880b14433b7bee2b1d53ef8de3aa0d835fb3742e69230f1

Tx prefix hash: bb9877b63f844afa9163a1e00b3f341d9c3b881e1d82518937f6a91a532d01e3
Tx public key: 9a2805e8f6838baac5d7e54eaf7ea1e3b5c50d40c7dc6757b5cdf50ecd3a2648
Timestamp: 1672878950 Timestamp [UCT]: 2023-01-05 00:35:50 Age [y:d:h:m:s]: 01:334:05:02:27
Block: 667753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499886 RingCT/type: yes/0
Extra: 019a2805e8f6838baac5d7e54eaf7ea1e3b5c50d40c7dc6757b5cdf50ecd3a264802110000000152542ceb000000000000000000

1 output(s) for total of 3.762331633000 dcy

stealth address amount amount idx
00: 0cbd0b461f407f49d41f0922d08882b3b73ad38ddc37bc31067805fdb7adbd0f 3.762331633000 1108970 of 0

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": 667763, "vin": [ { "gen": { "height": 667753 } } ], "vout": [ { "amount": 3762331633, "target": { "key": "0cbd0b461f407f49d41f0922d08882b3b73ad38ddc37bc31067805fdb7adbd0f" } } ], "extra": [ 1, 154, 40, 5, 232, 246, 131, 139, 170, 197, 215, 229, 78, 175, 126, 161, 227, 181, 197, 13, 64, 199, 220, 103, 87, 181, 205, 245, 14, 205, 58, 38, 72, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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