Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b1b4b3c29a957093fbbd9460b9e359ca8cf88889c3d26d7a272316364db1cf1

Tx prefix hash: f88d771e1e7862104ca1e81d6a1bbaab69278260f8ef839e12f17dc6920d6e8a
Tx public key: 881f4aeb4fdf3100efd384503c4a7af00c95eb129b0eed49f4455b4b28ed02b6
Timestamp: 1685381086 Timestamp [UCT]: 2023-05-29 17:24:46 Age [y:d:h:m:s]: 02:189:03:31:30
Block: 770799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 655009 RingCT/type: yes/0
Extra: 01881f4aeb4fdf3100efd384503c4a7af00c95eb129b0eed49f4455b4b28ed02b602110000000775e3f0e9000000000000000000

1 output(s) for total of 1.714048521000 dcy

stealth address amount amount idx
00: bb6c3cf29a8d4d1c607c9f0a0644329dde9cb3940bbe7e1208a01eb6c0abee3e 1.714048521000 1220130 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": 770809, "vin": [ { "gen": { "height": 770799 } } ], "vout": [ { "amount": 1714048521, "target": { "key": "bb6c3cf29a8d4d1c607c9f0a0644329dde9cb3940bbe7e1208a01eb6c0abee3e" } } ], "extra": [ 1, 136, 31, 74, 235, 79, 223, 49, 0, 239, 211, 132, 80, 60, 74, 122, 240, 12, 149, 235, 18, 155, 14, 237, 73, 244, 69, 91, 75, 40, 237, 2, 182, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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