Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9cde5058c3cfeb234d11576b377c10f8a0dc5ae40692e55cb32d9cc11e99b2b

Tx prefix hash: 4a286f5ae74e21484d8c828ab93539e7c349795f654b38d5071035f74745e1f2
Tx public key: f9f6e7ff671af071b8042f40b5af1bccd9d9d07a689c3821e589b42216696254
Timestamp: 1719508067 Timestamp [UCT]: 2024-06-27 17:07:47 Age [y:d:h:m:s]: 00:321:16:23:31
Block: 1053467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229895 RingCT/type: yes/0
Extra: 01f9f6e7ff671af071b8042f40b5af1bccd9d9d07a689c3821e589b4221669625402110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f1886585d0e6288dcba3146714595031314ae4108f8dec3f8fef52f024158f5 0.600000000000 1523814 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": 1053477, "vin": [ { "gen": { "height": 1053467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f1886585d0e6288dcba3146714595031314ae4108f8dec3f8fef52f024158f5" } } ], "extra": [ 1, 249, 246, 231, 255, 103, 26, 240, 113, 184, 4, 47, 64, 181, 175, 27, 204, 217, 217, 208, 122, 104, 156, 56, 33, 229, 137, 180, 34, 22, 105, 98, 84, 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