Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f916d6a5fc1db01863a3dd4563e0ba5d0a635e141add35f01fc45751a9ef94da

Tx prefix hash: c5e45d2eeb473eb6205e9024d53440a7bb15f757f72fde18e9ecbd54a00f2d9d
Tx public key: 457e2c669b2b83bc024f26f6bb587096edf48529be4e06c6486977f91ff2ef47
Timestamp: 1745050543 Timestamp [UCT]: 2025-04-19 08:15:43 Age [y:d:h:m:s]: 00:216:07:09:33
Block: 1264730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152301 RingCT/type: yes/0
Extra: 01457e2c669b2b83bc024f26f6bb587096edf48529be4e06c6486977f91ff2ef470211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67ccd6ccc3d42e337af1d042a0f6fdea6e66b5c746ede7421b45ba908dc16b97 0.600000000000 1751931 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": 1264740, "vin": [ { "gen": { "height": 1264730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67ccd6ccc3d42e337af1d042a0f6fdea6e66b5c746ede7421b45ba908dc16b97" } } ], "extra": [ 1, 69, 126, 44, 102, 155, 43, 131, 188, 2, 79, 38, 246, 187, 88, 112, 150, 237, 244, 133, 41, 190, 78, 6, 198, 72, 105, 119, 249, 31, 242, 239, 71, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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