Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 289cb8bec4fa5c95f4f861a9298c857cfdd5c5c4784b5e6dccfa465a3baa4bdf

Tx prefix hash: 4254297fab6cd76a274b7d60dc8bc42c8435a8d9acfa5e2e054ea0742fc0a5ac
Tx public key: 91d78dfcaa720fda118fc33b8622b9938349c829d57173d95e90ab64c2fcb55d
Timestamp: 1745340228 Timestamp [UCT]: 2025-04-22 16:43:48 Age [y:d:h:m:s]: 00:020:08:09:48
Block: 1267124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14547 RingCT/type: yes/0
Extra: 0191d78dfcaa720fda118fc33b8622b9938349c829d57173d95e90ab64c2fcb55d021100000005dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a9db555f794d293a58b6b47cf3dac2d787c07e33d30eefed5099e4af50894fd 0.600000000000 1754351 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": 1267134, "vin": [ { "gen": { "height": 1267124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a9db555f794d293a58b6b47cf3dac2d787c07e33d30eefed5099e4af50894fd" } } ], "extra": [ 1, 145, 215, 141, 252, 170, 114, 15, 218, 17, 143, 195, 59, 134, 34, 185, 147, 131, 73, 200, 41, 213, 113, 115, 217, 94, 144, 171, 100, 194, 252, 181, 93, 2, 17, 0, 0, 0, 5, 219, 181, 113, 193, 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