Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a7d5ae7194f3510cb1f0c8fe77408c729a27bb0cd84f6da3626cbdde921f75a

Tx prefix hash: 889b8d17e234e86a8eb7aa046494f9bccc1bf848cda09a063fef3f798768c15a
Tx public key: 8dd18ff1e853bb14e36bfa43745c8baddf0d96470e0dfb0a4b849542ffb5b912
Timestamp: 1695686016 Timestamp [UCT]: 2023-09-25 23:53:36 Age [y:d:h:m:s]: 01:116:10:31:58
Block: 856178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344470 RingCT/type: yes/0
Extra: 018dd18ff1e853bb14e36bfa43745c8baddf0d96470e0dfb0a4b849542ffb5b91202110000000275e3f0e9000000000000000000

1 output(s) for total of 0.893566579000 dcy

stealth address amount amount idx
00: c35e329a15ec90122633e9584a94fd7c3128f4af6bf279f67c8af2603f3ac72d 0.893566579000 1310240 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": 856188, "vin": [ { "gen": { "height": 856178 } } ], "vout": [ { "amount": 893566579, "target": { "key": "c35e329a15ec90122633e9584a94fd7c3128f4af6bf279f67c8af2603f3ac72d" } } ], "extra": [ 1, 141, 209, 143, 241, 232, 83, 187, 20, 227, 107, 250, 67, 116, 92, 139, 173, 223, 13, 150, 71, 14, 13, 251, 10, 75, 132, 149, 66, 255, 181, 185, 18, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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