Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 777c4304fa7273bf51c5e7ca4728d0310f9d6a35f57c5d8100c143975fce23c9

Tx prefix hash: 3e9a58c6b3962813c3740e7711331044501e64ae8bda893700ee0f045c37c2b5
Tx public key: 43b74350d1d5cc910cfe947dd59218248832d4290e776a4d2a4aebe413c425d6
Timestamp: 1732275072 Timestamp [UCT]: 2024-11-22 11:31:12 Age [y:d:h:m:s]: 00:132:08:47:52
Block: 1159222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94411 RingCT/type: yes/0
Extra: 0143b74350d1d5cc910cfe947dd59218248832d4290e776a4d2a4aebe413c425d6021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d9703a6ec7f341f074603646963a9e258e0f9701555779ee615bfeae8d79ecc 0.600000000000 1644855 of 15

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": 1159232, "vin": [ { "gen": { "height": 1159222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d9703a6ec7f341f074603646963a9e258e0f9701555779ee615bfeae8d79ecc" } } ], "extra": [ 1, 67, 183, 67, 80, 209, 213, 204, 145, 12, 254, 148, 125, 213, 146, 24, 36, 136, 50, 212, 41, 14, 119, 106, 77, 42, 74, 235, 228, 19, 196, 37, 214, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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