Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8c139b3ed2c123760d57b6bc5402edb144c50c8cecc9fe39f81b3c59c0092b4

Tx prefix hash: 94d13bbbb20899aaf71eee9fa8a1dc832825dfabb0426c0fc0400e525fef75c7
Tx public key: 5cc54f4935d60b4c386c6bb9a5559e844d3c52b5b72b38f49ff4f8b2f8421b37
Timestamp: 1701485182 Timestamp [UCT]: 2023-12-02 02:46:22 Age [y:d:h:m:s]: 01:340:04:14:51
Block: 904047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501992 RingCT/type: yes/0
Extra: 015cc54f4935d60b4c386c6bb9a5559e844d3c52b5b72b38f49ff4f8b2f8421b3702110000000e75e3f0e9000000000000000000

1 output(s) for total of 0.620178889000 dcy

stealth address amount amount idx
00: e50085bf9ac539612038613c41c863a5c14d0af009b4e02529392da267763cc4 0.620178889000 1360750 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": 904057, "vin": [ { "gen": { "height": 904047 } } ], "vout": [ { "amount": 620178889, "target": { "key": "e50085bf9ac539612038613c41c863a5c14d0af009b4e02529392da267763cc4" } } ], "extra": [ 1, 92, 197, 79, 73, 53, 214, 11, 76, 56, 108, 107, 185, 165, 85, 158, 132, 77, 60, 82, 181, 183, 43, 56, 244, 159, 244, 248, 178, 248, 66, 27, 55, 2, 17, 0, 0, 0, 14, 117, 227, 240, 233, 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