Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7189bdcc221fe8200ed0b41359aa172606ad88aeb4e89b2caea346f67acffcb

Tx prefix hash: 27b3d16c7f7fcc05181966f37fea0f9b50583afc182c95dfdaa180216b80dc78
Tx public key: 5f9803f33657b14f4556427cf552d530bae4bd6a35620f94498c6b0a01a931f8
Timestamp: 1708148937 Timestamp [UCT]: 2024-02-17 05:48:57 Age [y:d:h:m:s]: 01:038:09:12:40
Block: 959298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288443 RingCT/type: yes/0
Extra: 015f9803f33657b14f4556427cf552d530bae4bd6a35620f94498c6b0a01a931f802110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3141dee5e821e2e2b5d9843a7b10d104caaab288d2f50366a64727d71dc17040 0.600000000000 1418833 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": 959308, "vin": [ { "gen": { "height": 959298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3141dee5e821e2e2b5d9843a7b10d104caaab288d2f50366a64727d71dc17040" } } ], "extra": [ 1, 95, 152, 3, 243, 54, 87, 177, 79, 69, 86, 66, 124, 245, 82, 213, 48, 186, 228, 189, 106, 53, 98, 15, 148, 73, 140, 107, 10, 1, 169, 49, 248, 2, 17, 0, 0, 0, 11, 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