Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2592d4f3a64f91de26dd3d547c60674fd19183eebfc55d7edd867babad45c7c

Tx prefix hash: ea31136edeec51600bb5d7923694c1a4af05587c9d5014fbc579d625fd73d77c
Tx public key: aa477fe7b48955052855f5203fb45e3f3d91dc227d8fa62a2f2eed6e4d02c5b4
Timestamp: 1749898577 Timestamp [UCT]: 2025-06-14 10:56:17 Age [y:d:h:m:s]: 00:232:06:46:39
Block: 1304793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163692 RingCT/type: yes/0
Extra: 01aa477fe7b48955052855f5203fb45e3f3d91dc227d8fa62a2f2eed6e4d02c5b4021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dda60a4d84fe7097a4fc977bb0d676e3ffc33e46a4ab7299a2936c8c8e9988fa 0.600000000000 1792386 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": 1304803, "vin": [ { "gen": { "height": 1304793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dda60a4d84fe7097a4fc977bb0d676e3ffc33e46a4ab7299a2936c8c8e9988fa" } } ], "extra": [ 1, 170, 71, 127, 231, 180, 137, 85, 5, 40, 85, 245, 32, 63, 180, 94, 63, 61, 145, 220, 34, 125, 143, 166, 42, 47, 46, 237, 110, 77, 2, 197, 180, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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