Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b454c8c384491a81a11cd3381097378c2d8da6d2a383a2b4f0ec7daac0d99430

Tx prefix hash: cb5a5c662031597da435dd1ccca9da7f57bf9106348a26c19a48eb46e9d0febe
Tx public key: 81cd08a58d49108f349e6c9c7734cab8b74d195ea3bef5bdcc19c362d33874f9
Timestamp: 1709407529 Timestamp [UCT]: 2024-03-02 19:25:29 Age [y:d:h:m:s]: 01:219:01:51:01
Block: 969744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415243 RingCT/type: yes/0
Extra: 0181cd08a58d49108f349e6c9c7734cab8b74d195ea3bef5bdcc19c362d33874f902110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41b10daf710a13424559804c6f47aa54c841781f3e3b3becb3a36692ceaee641 0.600000000000 1429585 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": 969754, "vin": [ { "gen": { "height": 969744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41b10daf710a13424559804c6f47aa54c841781f3e3b3becb3a36692ceaee641" } } ], "extra": [ 1, 129, 205, 8, 165, 141, 73, 16, 143, 52, 158, 108, 156, 119, 52, 202, 184, 183, 77, 25, 94, 163, 190, 245, 189, 204, 25, 195, 98, 211, 56, 116, 249, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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