Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17f13991079e35cd2d8a5df2afe3f5eef9f247564f948f759deb171d86fc9a8c

Tx prefix hash: 28479239a8dc2e7bd4b5be0bab4e68a241fed7223990552a37d43c4865e81862
Tx public key: e9ce2da620212788491af6dfa0f1a087f1274853dc37f0acd391f2f0a7407b10
Timestamp: 1745760692 Timestamp [UCT]: 2025-04-27 13:31:32 Age [y:d:h:m:s]: 00:206:11:57:49
Block: 1270612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145305 RingCT/type: yes/0
Extra: 01e9ce2da620212788491af6dfa0f1a087f1274853dc37f0acd391f2f0a7407b1002110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ce73a742b62512ecc54f9b2cfa8069cb5c081224b7cd3f8eb0ea19340614ff2 0.600000000000 1757855 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": 1270622, "vin": [ { "gen": { "height": 1270612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ce73a742b62512ecc54f9b2cfa8069cb5c081224b7cd3f8eb0ea19340614ff2" } } ], "extra": [ 1, 233, 206, 45, 166, 32, 33, 39, 136, 73, 26, 246, 223, 160, 241, 160, 135, 241, 39, 72, 83, 220, 55, 240, 172, 211, 145, 242, 240, 167, 64, 123, 16, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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