Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb0d12ec77f10df85d12b0b322468b6857f6dcd437b1f462c78b4d2436f3a5f4

Tx prefix hash: 0041afdb448e6ea2a6c91d51fdf6de13e4bc4048e54f91ac50ab2e1550441f2f
Tx public key: 0f1119d48ee085761949f83f932f5a5ef39561a079ccd38680abb3fd25efa723
Timestamp: 1736490329 Timestamp [UCT]: 2025-01-10 06:25:29 Age [y:d:h:m:s]: 00:071:01:07:04
Block: 1194134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50545 RingCT/type: yes/0
Extra: 010f1119d48ee085761949f83f932f5a5ef39561a079ccd38680abb3fd25efa7230211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5189f1e51c3927151e1f51f82ef2d96cc213e756e97dd6e64fe29cd7b71880a 0.600000000000 1680701 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": 1194144, "vin": [ { "gen": { "height": 1194134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5189f1e51c3927151e1f51f82ef2d96cc213e756e97dd6e64fe29cd7b71880a" } } ], "extra": [ 1, 15, 17, 25, 212, 142, 224, 133, 118, 25, 73, 248, 63, 147, 47, 90, 94, 243, 149, 97, 160, 121, 204, 211, 134, 128, 171, 179, 253, 37, 239, 167, 35, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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