Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ab7c66349a5b13be1598695770f64d3f6f0d7413b5031062499146b357a7b34

Tx prefix hash: 65687ee2faab4e490003f96afb0f6d98b12528869732a2f843c815b0a30ca8e8
Tx public key: 44cfd04dd47a3d05808038d948749cb7404ee367f84b6180bd1253f39cb9c0cd
Timestamp: 1733319832 Timestamp [UCT]: 2024-12-04 13:43:52 Age [y:d:h:m:s]: 00:119:13:52:04
Block: 1167876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85255 RingCT/type: yes/0
Extra: 0144cfd04dd47a3d05808038d948749cb7404ee367f84b6180bd1253f39cb9c0cd021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa01ee1699a2d2b8f24c5fcb2127dcd4e7a6a91e37c83d823d2c5270195fd87c 0.600000000000 1653579 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": 1167886, "vin": [ { "gen": { "height": 1167876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa01ee1699a2d2b8f24c5fcb2127dcd4e7a6a91e37c83d823d2c5270195fd87c" } } ], "extra": [ 1, 68, 207, 208, 77, 212, 122, 61, 5, 128, 128, 56, 217, 72, 116, 156, 183, 64, 78, 227, 103, 248, 75, 97, 128, 189, 18, 83, 243, 156, 185, 192, 205, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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