Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb54c28cebf9e2ef76ae5668b0cedab73eab0736a74cf25ab9dfbc77ecfb14db

Tx prefix hash: 3c765bdfd62a39fcc8347b20638f1bdaf3d1a9a1e1075da0577396d88c79b24e
Tx public key: cc40004e44f3a8e6b776b742c51c37e72d0ea7897c80973456ca24c2899b5929
Timestamp: 1677592514 Timestamp [UCT]: 2023-02-28 13:55:14 Age [y:d:h:m:s]: 02:093:12:34:21
Block: 706853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 588475 RingCT/type: yes/0
Extra: 01cc40004e44f3a8e6b776b742c51c37e72d0ea7897c80973456ca24c2899b592902110000000183600029000000000000000000

1 output(s) for total of 2.791916887000 dcy

stealth address amount amount idx
00: e026beda8a61fbbb44b3ac7caf2d434de70ab6d42a073ad2f3d1748dff39f82c 2.791916887000 1150612 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": 706863, "vin": [ { "gen": { "height": 706853 } } ], "vout": [ { "amount": 2791916887, "target": { "key": "e026beda8a61fbbb44b3ac7caf2d434de70ab6d42a073ad2f3d1748dff39f82c" } } ], "extra": [ 1, 204, 64, 0, 78, 68, 243, 168, 230, 183, 118, 183, 66, 197, 28, 55, 231, 45, 14, 167, 137, 124, 128, 151, 52, 86, 202, 36, 194, 137, 155, 89, 41, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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