Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b653344cf64e3c3c53ab8a19aa7bcbbedfac301a32a40189a888911c3bf65af

Tx prefix hash: d8689e0c64de073ba7384891c032a695bfbd77f0dab53b613cf8d9f2055fb43c
Tx public key: 2d1cd7f93d7a0eecd2ae546ae18cb59a67a0dba36c1b5d23e835e88ca64e18a2
Timestamp: 1579190465 Timestamp [UCT]: 2020-01-16 16:01:05 Age [y:d:h:m:s]: 04:315:22:31:57
Block: 46926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1115252 RingCT/type: yes/0
Extra: 012d1cd7f93d7a0eecd2ae546ae18cb59a67a0dba36c1b5d23e835e88ca64e18a2021100000008d81c26c0000000000000000000

1 output(s) for total of 429.057521398000 dcy

stealth address amount amount idx
00: 4735dfa08bc4e307e6fce845798f4dfd14991bf2dcd494ad04a61a58078aa648 429.057521398000 86566 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": 46936, "vin": [ { "gen": { "height": 46926 } } ], "vout": [ { "amount": 429057521398, "target": { "key": "4735dfa08bc4e307e6fce845798f4dfd14991bf2dcd494ad04a61a58078aa648" } } ], "extra": [ 1, 45, 28, 215, 249, 61, 122, 14, 236, 210, 174, 84, 106, 225, 140, 181, 154, 103, 160, 219, 163, 108, 27, 93, 35, 232, 53, 232, 140, 166, 78, 24, 162, 2, 17, 0, 0, 0, 8, 216, 28, 38, 192, 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