Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03bba6a2f77da0374c5a4cd145d596e9fcca7aa63009165b276883ffed31cc5f

Tx prefix hash: 78a68f54704bb540e3276ce2232b9575e1d0f8b5b6a342ab798f5d1fd471a445
Tx public key: f488dc6f5c5cc99c64384c7495b1cb24e473cee7090b0de4bf0231708356f2df
Timestamp: 1723917695 Timestamp [UCT]: 2024-08-17 18:01:35 Age [y:d:h:m:s]: 01:086:11:01:52
Block: 1090041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320249 RingCT/type: yes/0
Extra: 01f488dc6f5c5cc99c64384c7495b1cb24e473cee7090b0de4bf0231708356f2df021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b81ec77d39cc4ac96f613cb27634779901bd950ee1c080499dbbe7f85e9fe15 0.600000000000 1564664 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": 1090051, "vin": [ { "gen": { "height": 1090041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b81ec77d39cc4ac96f613cb27634779901bd950ee1c080499dbbe7f85e9fe15" } } ], "extra": [ 1, 244, 136, 220, 111, 92, 92, 201, 156, 100, 56, 76, 116, 149, 177, 203, 36, 228, 115, 206, 231, 9, 11, 13, 228, 191, 2, 49, 112, 131, 86, 242, 223, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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