Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cf881842c6af1ed664f5d4016051ca16130da9696dabce1a176fde9cb300e1c

Tx prefix hash: 34712a43cfa4841041eda3bf1c0dc0e6b02ed5d27c0344d361d9377b3e22cc19
Tx public key: 5b6fba28a9d2b0f065d4e0c799846367964c111416ba2fedb1706738c1b5ff97
Timestamp: 1713795723 Timestamp [UCT]: 2024-04-22 14:22:03 Age [y:d:h:m:s]: 00:265:11:51:29
Block: 1006119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190032 RingCT/type: yes/0
Extra: 015b6fba28a9d2b0f065d4e0c799846367964c111416ba2fedb1706738c1b5ff9702110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b67b6b722c1b74b1811f7e987f06df3c37198c5ec9ef89c2bde5980eb050506d 0.600000000000 1467041 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": 1006129, "vin": [ { "gen": { "height": 1006119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b67b6b722c1b74b1811f7e987f06df3c37198c5ec9ef89c2bde5980eb050506d" } } ], "extra": [ 1, 91, 111, 186, 40, 169, 210, 176, 240, 101, 212, 224, 199, 153, 132, 99, 103, 150, 76, 17, 20, 22, 186, 47, 237, 177, 112, 103, 56, 193, 181, 255, 151, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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