Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 215471094cf0c53cc98a5b4ff896326c6d8a98fbbcfc4bbcf73442a11de08465

Tx prefix hash: ed9a7142cc1631473a6755f2583fe5f0046cc36bb906d2443a7869c62fbacd93
Tx public key: 8d269404ee7936a1b114aa8bb193ab71a2c0093ff6d46477e473a84cb580b90d
Timestamp: 1744154082 Timestamp [UCT]: 2025-04-08 23:14:42 Age [y:d:h:m:s]: 00:251:22:46:02
Block: 1257297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177839 RingCT/type: yes/0
Extra: 018d269404ee7936a1b114aa8bb193ab71a2c0093ff6d46477e473a84cb580b90d021100000001dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddcff5e44777c31d0c89daad10ba2d751a79b8f2e29cff0bb9c57e6b3cade75a 0.600000000000 1744416 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": 1257307, "vin": [ { "gen": { "height": 1257297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddcff5e44777c31d0c89daad10ba2d751a79b8f2e29cff0bb9c57e6b3cade75a" } } ], "extra": [ 1, 141, 38, 148, 4, 238, 121, 54, 161, 177, 20, 170, 139, 177, 147, 171, 113, 162, 192, 9, 63, 246, 212, 100, 119, 228, 115, 168, 76, 181, 128, 185, 13, 2, 17, 0, 0, 0, 1, 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