Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ba9c5eabc5d8db1b4ab082d992a5d3b7a05b3ea99766b1eaaddceaf0a4b710f

Tx prefix hash: 526e9d421f69fa991d1daf9308f04f7b5c062e8119d42f8d17e95973701a63d0
Tx public key: cf25916e6b54e26fc4de1a17f3c1d0f568a164eaeab56934c6f9eed775736156
Timestamp: 1700404766 Timestamp [UCT]: 2023-11-19 14:39:26 Age [y:d:h:m:s]: 01:158:20:25:16
Block: 895103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374721 RingCT/type: yes/0
Extra: 01cf25916e6b54e26fc4de1a17f3c1d0f568a164eaeab56934c6f9eed77573615602110000000933af99f4000000000000000000

1 output(s) for total of 0.663975686000 dcy

stealth address amount amount idx
00: 26f7ff001ac9793f05a5875e116d39401ba6e42c13ad47d329b0c7271b0c9efd 0.663975686000 1351326 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": 895113, "vin": [ { "gen": { "height": 895103 } } ], "vout": [ { "amount": 663975686, "target": { "key": "26f7ff001ac9793f05a5875e116d39401ba6e42c13ad47d329b0c7271b0c9efd" } } ], "extra": [ 1, 207, 37, 145, 110, 107, 84, 226, 111, 196, 222, 26, 23, 243, 193, 208, 245, 104, 161, 100, 234, 234, 181, 105, 52, 198, 249, 238, 215, 117, 115, 97, 86, 2, 17, 0, 0, 0, 9, 51, 175, 153, 244, 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