Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 589674965fffbf142721419c23d2ebbcf0eaceae4d531eef679c95ab0ce03b00

Tx prefix hash: 99492ce1801dbfc763dd81639a80dff090af6b434ca75b9abd277b72ed0228d5
Tx public key: a4a7ea543c310250b6dda1dcf041c83000cd6e802681d1e3b036e5f2069e6840
Timestamp: 1580976218 Timestamp [UCT]: 2020-02-06 08:03:38 Age [y:d:h:m:s]: 04:274:01:24:16
Block: 59628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1087368 RingCT/type: yes/0
Extra: 01a4a7ea543c310250b6dda1dcf041c83000cd6e802681d1e3b036e5f2069e6840021100000002c71d3ff9000000000000000000

1 output(s) for total of 389.429190713000 dcy

stealth address amount amount idx
00: 67972bb57143704a5bd34eb14f8a7dd1bc99bfced32bdb84b73b5c8aae5f7ce3 389.429190713000 110080 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": 59638, "vin": [ { "gen": { "height": 59628 } } ], "vout": [ { "amount": 389429190713, "target": { "key": "67972bb57143704a5bd34eb14f8a7dd1bc99bfced32bdb84b73b5c8aae5f7ce3" } } ], "extra": [ 1, 164, 167, 234, 84, 60, 49, 2, 80, 182, 221, 161, 220, 240, 65, 200, 48, 0, 205, 110, 128, 38, 129, 209, 227, 176, 54, 229, 242, 6, 158, 104, 64, 2, 17, 0, 0, 0, 2, 199, 29, 63, 249, 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