Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07791bc160b590f962171ff93eda0587f701bf64ea5907a73e2f4f4255998a25

Tx prefix hash: 4ecb5cb52c19897f7fe9e4320708e5795186c25c93955427a44c8cfbbbe06d82
Tx public key: f6c60093660ce03f1a17be8c1a5117c3f7e83e2c36c5b034e8329c96f26e2d8e
Timestamp: 1723888205 Timestamp [UCT]: 2024-08-17 09:50:05 Age [y:d:h:m:s]: 00:275:13:21:48
Block: 1089800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196829 RingCT/type: yes/0
Extra: 01f6c60093660ce03f1a17be8c1a5117c3f7e83e2c36c5b034e8329c96f26e2d8e021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b013121b09f0743e17a4206b4e8c92c9477aaaeb78c1ef9aaca96032cd44ecae 0.600000000000 1564423 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": 1089810, "vin": [ { "gen": { "height": 1089800 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b013121b09f0743e17a4206b4e8c92c9477aaaeb78c1ef9aaca96032cd44ecae" } } ], "extra": [ 1, 246, 198, 0, 147, 102, 12, 224, 63, 26, 23, 190, 140, 26, 81, 23, 195, 247, 232, 62, 44, 54, 197, 176, 52, 232, 50, 156, 150, 242, 110, 45, 142, 2, 17, 0, 0, 0, 5, 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