Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30e8914bcf15a8e1fc9cd3b23fc98a6240a4725096ee99f07f1d1f35cb9ed00d

Tx prefix hash: 5f8f2ef00457a0546f1d8e5f09fd674c67a2e90c235597ed6be833137a28b64f
Tx public key: fd6fa3ed298df7031ce41c26c0fdc26101437f0fa35c3f263d1502b9a9254b15
Timestamp: 1582975927 Timestamp [UCT]: 2020-02-29 11:32:07 Age [y:d:h:m:s]: 05:004:21:02:51
Block: 74007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1157826 RingCT/type: yes/0
Extra: 01fd6fa3ed298df7031ce41c26c0fdc26101437f0fa35c3f263d1502b9a9254b1502110000009f03d36d11000000000000000000

1 output(s) for total of 348.967422685000 dcy

stealth address amount amount idx
00: f684f68c48dcf8815757b770ab2a4713a8524b9d7d8ed216cc2fb72e9292385e 348.967422685000 136779 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": 74017, "vin": [ { "gen": { "height": 74007 } } ], "vout": [ { "amount": 348967422685, "target": { "key": "f684f68c48dcf8815757b770ab2a4713a8524b9d7d8ed216cc2fb72e9292385e" } } ], "extra": [ 1, 253, 111, 163, 237, 41, 141, 247, 3, 28, 228, 28, 38, 192, 253, 194, 97, 1, 67, 127, 15, 163, 92, 63, 38, 61, 21, 2, 185, 169, 37, 75, 21, 2, 17, 0, 0, 0, 159, 3, 211, 109, 17, 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