Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f02361821621d12823b56125b10fd26dccc66af9c9ae66a006bc6643d76d41ba

Tx prefix hash: b15520ad9a168d333179e99f6441f68606f70f2dfaa443915a927decc7ef5e0c
Tx public key: 0cb0591c352727f6a2db20d25d4e65d186d0808e4d35e2d6633dec1fd2c97499
Timestamp: 1730295445 Timestamp [UCT]: 2024-10-30 13:37:25 Age [y:d:h:m:s]: 00:140:17:06:18
Block: 1142831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100409 RingCT/type: yes/0
Extra: 010cb0591c352727f6a2db20d25d4e65d186d0808e4d35e2d6633dec1fd2c974990211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f8ed00af1ac344c18a5ed2e579f33426cd26d3b9708851c5e9070ecec256b90 0.600000000000 1626686 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": 1142841, "vin": [ { "gen": { "height": 1142831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f8ed00af1ac344c18a5ed2e579f33426cd26d3b9708851c5e9070ecec256b90" } } ], "extra": [ 1, 12, 176, 89, 28, 53, 39, 39, 246, 162, 219, 32, 210, 93, 78, 101, 209, 134, 208, 128, 142, 77, 53, 226, 214, 99, 61, 236, 31, 210, 201, 116, 153, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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