Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59b90bf6b88938ba4a12d68967bd074bd9ddd1009296446a542be7c1a5e831b3

Tx prefix hash: eb360a8e19cfbe2841b2a2ac1f7ea8e3b7a3331b1852d6de477c307b52819029
Tx public key: 2c038136a3e4e5e4e828ae95d3f30215d49427aaa18537e0304eef4fafa77627
Timestamp: 1657418235 Timestamp [UCT]: 2022-07-10 01:57:15 Age [y:d:h:m:s]: 03:113:22:23:25
Block: 540427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 861143 RingCT/type: yes/0
Extra: 012c038136a3e4e5e4e828ae95d3f30215d49427aaa18537e0304eef4fafa7762702110000000ac9067537000000000000000000

1 output(s) for total of 9.938964820000 dcy

stealth address amount amount idx
00: 04fc6ee0b0996b0b515f92043fa61c3e55a391f982df432fe62783eab3493101 9.938964820000 970660 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": 540437, "vin": [ { "gen": { "height": 540427 } } ], "vout": [ { "amount": 9938964820, "target": { "key": "04fc6ee0b0996b0b515f92043fa61c3e55a391f982df432fe62783eab3493101" } } ], "extra": [ 1, 44, 3, 129, 54, 163, 228, 229, 228, 232, 40, 174, 149, 211, 243, 2, 21, 212, 148, 39, 170, 161, 133, 55, 224, 48, 78, 239, 79, 175, 167, 118, 39, 2, 17, 0, 0, 0, 10, 201, 6, 117, 55, 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