Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7af3332364fd34765af297e5d29fb7d8690a30feac45c4f03c37ba5bbf1ee75

Tx prefix hash: 0c4661b21d1d4320e7785992516f5304fb4f37d6517d46eb36d27793c8c5205e
Tx public key: d663768e741193800e0e6ef170f1a106712216e23162600c375ba8e7c919046c
Timestamp: 1641067770 Timestamp [UCT]: 2022-01-01 20:09:30 Age [y:d:h:m:s]: 02:323:06:59:34
Block: 408379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 749158 RingCT/type: yes/0
Extra: 01d663768e741193800e0e6ef170f1a106712216e23162600c375ba8e7c919046c02110000000758821d9c000000000000000000

1 output(s) for total of 27.218938602000 dcy

stealth address amount amount idx
00: 60d905fcbc976dc66c42a744f9e37638e403ff76aabd3cf4b2d05dd8d17f04fe 27.218938602000 810396 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": 408389, "vin": [ { "gen": { "height": 408379 } } ], "vout": [ { "amount": 27218938602, "target": { "key": "60d905fcbc976dc66c42a744f9e37638e403ff76aabd3cf4b2d05dd8d17f04fe" } } ], "extra": [ 1, 214, 99, 118, 142, 116, 17, 147, 128, 14, 14, 110, 241, 112, 241, 161, 6, 113, 34, 22, 226, 49, 98, 96, 12, 55, 91, 168, 231, 201, 25, 4, 108, 2, 17, 0, 0, 0, 7, 88, 130, 29, 156, 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