Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb8f35fa3eafaa207f74304e3e2534e63bb8d70f150f7d45f9570c73a6784788

Tx prefix hash: 4d37e90fe68c3492371b5c0fd5431f902dcbbc65b070702326e397b83dd6c518
Tx public key: 441acf8ae60552c48bcc3ac754d8b39d5fb6bc57aa987d03a12604b92cffef99
Timestamp: 1631393812 Timestamp [UCT]: 2021-09-11 20:56:52 Age [y:d:h:m:s]: 03:263:18:48:10
Block: 331872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 963849 RingCT/type: yes/0
Extra: 01441acf8ae60552c48bcc3ac754d8b39d5fb6bc57aa987d03a12604b92cffef99021100000021f60c5d7e000000000000000000

1 output(s) for total of 48.794485288000 dcy

stealth address amount amount idx
00: 02e60060e12aa21a4d3abbd58110c20a97f45914614716ae606c8717340862d9 48.794485288000 685605 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": 331882, "vin": [ { "gen": { "height": 331872 } } ], "vout": [ { "amount": 48794485288, "target": { "key": "02e60060e12aa21a4d3abbd58110c20a97f45914614716ae606c8717340862d9" } } ], "extra": [ 1, 68, 26, 207, 138, 230, 5, 82, 196, 139, 204, 58, 199, 84, 216, 179, 157, 95, 182, 188, 87, 170, 152, 125, 3, 161, 38, 4, 185, 44, 255, 239, 153, 2, 17, 0, 0, 0, 33, 246, 12, 93, 126, 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