Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9ccdcfafea0c085ca9e1a920a0f80465516a0935bced484bcf39cb2f56f266a

Tx prefix hash: 949a2cf51519919c7a3d23760addeebd671a4f1491f6e262bb03b99c34d53f42
Tx public key: 5aa1f8aabb8834bdc26be055047717ebe61043416d8d6077371d29dd8fd6cfa7
Timestamp: 1727412334 Timestamp [UCT]: 2024-09-27 04:45:34 Age [y:d:h:m:s]: 00:170:07:36:08
Block: 1119014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121540 RingCT/type: yes/0
Extra: 015aa1f8aabb8834bdc26be055047717ebe61043416d8d6077371d29dd8fd6cfa702110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d8b510b909e8073780deb78f86dc9bd3a47af7069b26cd16052f3f368d300aa 0.600000000000 1600407 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": 1119024, "vin": [ { "gen": { "height": 1119014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d8b510b909e8073780deb78f86dc9bd3a47af7069b26cd16052f3f368d300aa" } } ], "extra": [ 1, 90, 161, 248, 170, 187, 136, 52, 189, 194, 107, 224, 85, 4, 119, 23, 235, 230, 16, 67, 65, 109, 141, 96, 119, 55, 29, 41, 221, 143, 214, 207, 167, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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