Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5420849627a381c98a85accdbba958f57b01b1fce93a6104d68a1ba6e88ce7a7

Tx prefix hash: f5885559d5a4335e36dd1b51020d9d286ca3ae3f7f3967df6f53eace1e5a74e5
Tx public key: cb61c3057d395c6002cc6717e5053d5e87af4bf1179cf2e861703b66457e4df7
Timestamp: 1582383457 Timestamp [UCT]: 2020-02-22 14:57:37 Age [y:d:h:m:s]: 05:256:14:56:58
Block: 70237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1334350 RingCT/type: yes/0
Extra: 01cb61c3057d395c6002cc6717e5053d5e87af4bf1179cf2e861703b66457e4df702110000000212c4732d000000000000000000

1 output(s) for total of 359.150491882000 dcy

stealth address amount amount idx
00: 838a26c3dea7dbbb01500ef474d8507a517b3847e7457cddad1abe49c54429bd 359.150491882000 129708 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": 70247, "vin": [ { "gen": { "height": 70237 } } ], "vout": [ { "amount": 359150491882, "target": { "key": "838a26c3dea7dbbb01500ef474d8507a517b3847e7457cddad1abe49c54429bd" } } ], "extra": [ 1, 203, 97, 195, 5, 125, 57, 92, 96, 2, 204, 103, 23, 229, 5, 61, 94, 135, 175, 75, 241, 23, 156, 242, 232, 97, 112, 59, 102, 69, 126, 77, 247, 2, 17, 0, 0, 0, 2, 18, 196, 115, 45, 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