Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6621ff6e9fc308f29e9c74c6fa3d4e3c0816b1ce3131b81fba44f972f8f59d6d

Tx prefix hash: 3bf152369483e944b622e87224e6b9e685768992c1a60387fdd144d26aa7c926
Tx public key: 0aa58743588d65bffe0f1420ea5a34a4b87ced1291c0ec8394b67f8c68db4f70
Timestamp: 1624553979 Timestamp [UCT]: 2021-06-24 16:59:39 Age [y:d:h:m:s]: 03:154:16:23:01
Block: 283597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 877708 RingCT/type: yes/0
Extra: 010aa58743588d65bffe0f1420ea5a34a4b87ced1291c0ec8394b67f8c68db4f700211000000033634f08d000000000000000000

1 output(s) for total of 70.522212096000 dcy

stealth address amount amount idx
00: 0aa633cca94e8494973055c5b466cb60ef535b67225471ce30106252e79663ae 70.522212096000 593798 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": 283607, "vin": [ { "gen": { "height": 283597 } } ], "vout": [ { "amount": 70522212096, "target": { "key": "0aa633cca94e8494973055c5b466cb60ef535b67225471ce30106252e79663ae" } } ], "extra": [ 1, 10, 165, 135, 67, 88, 141, 101, 191, 254, 15, 20, 32, 234, 90, 52, 164, 184, 124, 237, 18, 145, 192, 236, 131, 148, 182, 127, 140, 104, 219, 79, 112, 2, 17, 0, 0, 0, 3, 54, 52, 240, 141, 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