Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 938055229a97f5687fcf8922d2f53d077a4a5ad56471a036a759b826a862dc25

Tx prefix hash: 1f4ced598c8727160ba7fe19e45ef48ae1650098e3bc5c4a2973ffe1041c97c5
Tx public key: e9b539c6a66b63148ee0f46de61907b63706e5f026307b390524df64f2a8b3a0
Timestamp: 1695679812 Timestamp [UCT]: 2023-09-25 22:10:12 Age [y:d:h:m:s]: 01:222:02:55:39
Block: 856128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419822 RingCT/type: yes/0
Extra: 01e9b539c6a66b63148ee0f46de61907b63706e5f026307b390524df64f2a8b3a002110000000233af99f4000000000000000000

1 output(s) for total of 0.893907514000 dcy

stealth address amount amount idx
00: 567fd52655fb7825eb64c2df3b3c177d5d1f378d5e2fa9e40a8e3dd89d679791 0.893907514000 1310186 of 0

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": 856138, "vin": [ { "gen": { "height": 856128 } } ], "vout": [ { "amount": 893907514, "target": { "key": "567fd52655fb7825eb64c2df3b3c177d5d1f378d5e2fa9e40a8e3dd89d679791" } } ], "extra": [ 1, 233, 181, 57, 198, 166, 107, 99, 20, 142, 224, 244, 109, 230, 25, 7, 182, 55, 6, 229, 240, 38, 48, 123, 57, 5, 36, 223, 100, 242, 168, 179, 160, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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