Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b93ea53c9437188111b2d95ef182e6692415948b8adce71b3a83928ffbbae20f

Tx prefix hash: e3160c7dd79381870814e9ad7d5e5eddf83af01bb3d0cfcde5af9990b33eea63
Tx public key: 5e9d7372fd1c687873976a64e3e1b9e03389dbc43ce70eea5dc41419b4e160f2
Timestamp: 1702741470 Timestamp [UCT]: 2023-12-16 15:44:30 Age [y:d:h:m:s]: 01:133:08:39:30
Block: 914471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356468 RingCT/type: yes/0
Extra: 015e9d7372fd1c687873976a64e3e1b9e03389dbc43ce70eea5dc41419b4e160f2021100000004faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b89536af541751e46b138d71a5a870322f655250b447724d1a78640bc79498b3 0.600000000000 1371787 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": 914481, "vin": [ { "gen": { "height": 914471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b89536af541751e46b138d71a5a870322f655250b447724d1a78640bc79498b3" } } ], "extra": [ 1, 94, 157, 115, 114, 253, 28, 104, 120, 115, 151, 106, 100, 227, 225, 185, 224, 51, 137, 219, 196, 60, 231, 14, 234, 93, 196, 20, 25, 180, 225, 96, 242, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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