Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7c86cd148b929458b8256d255315bbd3ff71e1ad7108321cc53fdab4eb275df

Tx prefix hash: 2af009c15b1e854fee8ab34a460083ef959de1c333db09d508d9cf7f06c55bc6
Tx public key: ddcb0b87f1947e4f40a5333e4df244f76e83aa09b6b6184f8141cf6ab604c766
Timestamp: 1636935137 Timestamp [UCT]: 2021-11-15 00:12:17 Age [y:d:h:m:s]: 03:120:15:54:03
Block: 374462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 864771 RingCT/type: yes/0
Extra: 01ddcb0b87f1947e4f40a5333e4df244f76e83aa09b6b6184f8141cf6ab604c76602110000000106faf294000000000000000000

1 output(s) for total of 35.257566619000 dcy

stealth address amount amount idx
00: d384364aabfb7a4ca3410d1174e35cca2b56e468cca364b968be9cbbb213f569 35.257566619000 757952 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": 374472, "vin": [ { "gen": { "height": 374462 } } ], "vout": [ { "amount": 35257566619, "target": { "key": "d384364aabfb7a4ca3410d1174e35cca2b56e468cca364b968be9cbbb213f569" } } ], "extra": [ 1, 221, 203, 11, 135, 241, 148, 126, 79, 64, 165, 51, 62, 77, 242, 68, 247, 110, 131, 170, 9, 182, 182, 24, 79, 129, 65, 207, 106, 182, 4, 199, 102, 2, 17, 0, 0, 0, 1, 6, 250, 242, 148, 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