Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b058d77d1cdd673f353f7cd4d48b838cf9e0d17b3bce7b6e8d548df8699c142b

Tx prefix hash: 2e918635c98e061bb330abde354e45f170ab0b81509cb8360993b42d3701b1b7
Tx public key: eff530e5484bda34f360e6ec4b855d86de883c612ab9350bbe6ff47cd4c2f65c
Timestamp: 1701495552 Timestamp [UCT]: 2023-12-02 05:39:12 Age [y:d:h:m:s]: 01:175:18:21:24
Block: 904135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386829 RingCT/type: yes/0
Extra: 01eff530e5484bda34f360e6ec4b855d86de883c612ab9350bbe6ff47cd4c2f65c02110000000346113aa8000000000000000000

1 output(s) for total of 0.619762647000 dcy

stealth address amount amount idx
00: 04d0c2b8143a6364158e048b16971e9b52a4f88385d9419165978aeecbb51ee8 0.619762647000 1360844 of 0

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": 904145, "vin": [ { "gen": { "height": 904135 } } ], "vout": [ { "amount": 619762647, "target": { "key": "04d0c2b8143a6364158e048b16971e9b52a4f88385d9419165978aeecbb51ee8" } } ], "extra": [ 1, 239, 245, 48, 229, 72, 75, 218, 52, 243, 96, 230, 236, 75, 133, 93, 134, 222, 136, 60, 97, 42, 185, 53, 11, 190, 111, 244, 124, 212, 194, 246, 92, 2, 17, 0, 0, 0, 3, 70, 17, 58, 168, 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