Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7178def5b9ff3c55c87a0a2cb636a919d9e70ab6f6c78931d9685d450a75ad8e

Tx prefix hash: 1cdaec7f88c6ef2e5b3fef15ab254c84ab2d29226a56442894335794b1e3395a
Tx public key: 9781375ba51a004400b605d4bf33ae91b65acc8df6ee9914e587a8aaf746b3cf
Timestamp: 1756157538 Timestamp [UCT]: 2025-08-25 21:32:18 Age [y:d:h:m:s]: 00:131:09:14:39
Block: 1354392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93911 RingCT/type: yes/0
Extra: 019781375ba51a004400b605d4bf33ae91b65acc8df6ee9914e587a8aaf746b3cf0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db135857e52b8e2d090f6c69987af108bcdd845f24d5afb5f14e90e43e12ef78 0.600000000000 1842379 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": 1354402, "vin": [ { "gen": { "height": 1354392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db135857e52b8e2d090f6c69987af108bcdd845f24d5afb5f14e90e43e12ef78" } } ], "extra": [ 1, 151, 129, 55, 91, 165, 26, 0, 68, 0, 182, 5, 212, 191, 51, 174, 145, 182, 90, 204, 141, 246, 238, 153, 20, 229, 135, 168, 170, 247, 70, 179, 207, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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