Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76d3f1d97e3fb812c9fc45801c71f39f9a148e7bcf2b03007e734b0d3bf308c1

Tx prefix hash: bf476e8f8d04f97068f79aa7214d27e9faddbcf67a366e1d8054311b36c90e26
Tx public key: baefe2a651847b72a3eb557b401fd6d3aa2f2451264de05c775ca65e2c2ec39f
Timestamp: 1593017821 Timestamp [UCT]: 2020-06-24 16:57:01 Age [y:d:h:m:s]: 04:229:07:21:50
Block: 110481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1103948 RingCT/type: yes/0
Extra: 01baefe2a651847b72a3eb557b401fd6d3aa2f2451264de05c775ca65e2c2ec39f02110000002b46a11e8a000000000000000000

1 output(s) for total of 264.199098567000 dcy

stealth address amount amount idx
00: e1be21ec0578f0d1420dcd199e1c38ae38c3b89a5e94dab937765df77466385f 264.199098567000 191367 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": 110491, "vin": [ { "gen": { "height": 110481 } } ], "vout": [ { "amount": 264199098567, "target": { "key": "e1be21ec0578f0d1420dcd199e1c38ae38c3b89a5e94dab937765df77466385f" } } ], "extra": [ 1, 186, 239, 226, 166, 81, 132, 123, 114, 163, 235, 85, 123, 64, 31, 214, 211, 170, 47, 36, 81, 38, 77, 224, 92, 119, 92, 166, 94, 44, 46, 195, 159, 2, 17, 0, 0, 0, 43, 70, 161, 30, 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