Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4bca42f3ce265cc5365f6c0b722152a03236a5eaaa8c171a6966729c02b1a57

Tx prefix hash: 94cdfe01e1e20c929a7a22d467f1b7d5eccfdd7dc0a30310b83da93f9fb10fc6
Tx public key: 91a367619d515bfa8bf0a9fab626a3144633c9eb953c3f523ee52058087c8f79
Timestamp: 1736622316 Timestamp [UCT]: 2025-01-11 19:05:16 Age [y:d:h:m:s]: 00:159:03:46:53
Block: 1195218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113438 RingCT/type: yes/0
Extra: 0191a367619d515bfa8bf0a9fab626a3144633c9eb953c3f523ee52058087c8f790211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 425357ccfad892a83c4a159f7eff80377309d31c16f20388c43fcd4fa9056ebd 0.600000000000 1681807 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": 1195228, "vin": [ { "gen": { "height": 1195218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "425357ccfad892a83c4a159f7eff80377309d31c16f20388c43fcd4fa9056ebd" } } ], "extra": [ 1, 145, 163, 103, 97, 157, 81, 91, 250, 139, 240, 169, 250, 182, 38, 163, 20, 70, 51, 201, 235, 149, 60, 63, 82, 62, 229, 32, 88, 8, 124, 143, 121, 2, 17, 0, 0, 0, 2, 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