Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 545cbcf683c783edd5b89a8efbd8133dc36a2e6087d0748e0cd8e99aef0d0ba2

Tx prefix hash: 8d709b79bf275ee3e52604295a1d59aab10c7598e938f2731593ddd93ca5b85f
Tx public key: 375d2fb83adc8ec1e27bfc690e2170e106fa04c1e8e7b35f0fae216fef0924de
Timestamp: 1694590022 Timestamp [UCT]: 2023-09-13 07:27:02 Age [y:d:h:m:s]: 01:242:17:43:47
Block: 847077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434606 RingCT/type: yes/0
Extra: 01375d2fb83adc8ec1e27bfc690e2170e106fa04c1e8e7b35f0fae216fef0924de0211000000044b8f5122000000000000000000

1 output(s) for total of 0.957816516000 dcy

stealth address amount amount idx
00: aebc594245017e5185ea94e38ad07e54561cc9988ec4673943356b04dded1d41 0.957816516000 1300577 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": 847087, "vin": [ { "gen": { "height": 847077 } } ], "vout": [ { "amount": 957816516, "target": { "key": "aebc594245017e5185ea94e38ad07e54561cc9988ec4673943356b04dded1d41" } } ], "extra": [ 1, 55, 93, 47, 184, 58, 220, 142, 193, 226, 123, 252, 105, 14, 33, 112, 225, 6, 250, 4, 193, 232, 231, 179, 95, 15, 174, 33, 111, 239, 9, 36, 222, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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