Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73ddddd7e3bd3d319c7d77a4e005cdeb76f8cbbe56a397d45aa8bcd360361444

Tx prefix hash: 632f3e325ef30365be8d3b357e9dfb1b4415ec9dcd644cec147db764312a044e
Tx public key: a9747a216d1a65d5b4448b0ae02a5251f3f13be540492e8aa045e87c91146a3b
Timestamp: 1701814358 Timestamp [UCT]: 2023-12-05 22:12:38 Age [y:d:h:m:s]: 01:145:13:11:42
Block: 906786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365202 RingCT/type: yes/0
Extra: 01a9747a216d1a65d5b4448b0ae02a5251f3f13be540492e8aa045e87c91146a3b021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.607353489000 dcy

stealth address amount amount idx
00: 6182ea6eeb6f4e04a7311357ba7c1663654148e507263d15ca6f274e68c34e81 0.607353489000 1363745 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": 906796, "vin": [ { "gen": { "height": 906786 } } ], "vout": [ { "amount": 607353489, "target": { "key": "6182ea6eeb6f4e04a7311357ba7c1663654148e507263d15ca6f274e68c34e81" } } ], "extra": [ 1, 169, 116, 122, 33, 109, 26, 101, 213, 180, 68, 139, 10, 224, 42, 82, 81, 243, 241, 59, 229, 64, 73, 46, 138, 160, 69, 232, 124, 145, 20, 106, 59, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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