Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73d6a2798bab2cec18531c28a3cc71e7d089f09a836ba1e01630a4be50b7df00

Tx prefix hash: d88789a5e3fba0d50793a53bf1d4f8c8480d4eea87954ac281969eea483e3f16
Tx public key: 3d2b450f60ec5cf874a1f33c84ba3d4faf925df16215110c432a39778db19f16
Timestamp: 1704274773 Timestamp [UCT]: 2024-01-03 09:39:33 Age [y:d:h:m:s]: 01:015:17:58:34
Block: 927187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272574 RingCT/type: yes/0
Extra: 013d2b450f60ec5cf874a1f33c84ba3d4faf925df16215110c432a39778db19f16021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07932a1338085a5e72c129d93bfc610181d1eb8b102f21786c7839eb2f57bcaf 0.600000000000 1384991 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": 927197, "vin": [ { "gen": { "height": 927187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07932a1338085a5e72c129d93bfc610181d1eb8b102f21786c7839eb2f57bcaf" } } ], "extra": [ 1, 61, 43, 69, 15, 96, 236, 92, 248, 116, 161, 243, 60, 132, 186, 61, 79, 175, 146, 93, 241, 98, 21, 17, 12, 67, 42, 57, 119, 141, 177, 159, 22, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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