Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d262cf154715af504512060b8d13a21992bf04d89e7da70e196f5abdfb7f770

Tx prefix hash: 5bff6b83cca30db8a9f06022976192ff207a7c9e73fa09b6c7caeab689074c38
Tx public key: 2839f5a4e3c6a6f4b17ec7123680e8b612a83fea8885f71a4674126d6811ac46
Timestamp: 1740726733 Timestamp [UCT]: 2025-02-28 07:12:13 Age [y:d:h:m:s]: 00:338:04:49:11
Block: 1228926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239383 RingCT/type: yes/0
Extra: 012839f5a4e3c6a6f4b17ec7123680e8b612a83fea8885f71a4674126d6811ac460211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4149a2594c067929428a89c7887f765d355dbebc177939e2b2835cba7a2a74c2 0.600000000000 1715807 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": 1228936, "vin": [ { "gen": { "height": 1228926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4149a2594c067929428a89c7887f765d355dbebc177939e2b2835cba7a2a74c2" } } ], "extra": [ 1, 40, 57, 245, 164, 227, 198, 166, 244, 177, 126, 199, 18, 54, 128, 232, 182, 18, 168, 63, 234, 136, 133, 247, 26, 70, 116, 18, 109, 104, 17, 172, 70, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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