Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8082873bed1a4ca8a2b5af9f1105bea1e97c300a1ee8ca2264d383a789fe562c

Tx prefix hash: 77d6d57959965b7f27ad1cf6649b33b15a1ee1be132e31d66109067a0025a78e
Tx public key: 58eadd5de12e46d718f902121d3dccccc12cd40ef7ad2ef722de19b5418de9d7
Timestamp: 1698596657 Timestamp [UCT]: 2023-10-29 16:24:17 Age [y:d:h:m:s]: 01:163:00:21:51
Block: 880325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377500 RingCT/type: yes/0
Extra: 0158eadd5de12e46d718f902121d3dccccc12cd40ef7ad2ef722de19b5418de9d702110000000533af99f4000000000000000000

1 output(s) for total of 0.743220785000 dcy

stealth address amount amount idx
00: b32d0d53dd3cbdff6a2b28f951d563c72add3b459819922a00ce610d746f8ffa 0.743220785000 1335875 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": 880335, "vin": [ { "gen": { "height": 880325 } } ], "vout": [ { "amount": 743220785, "target": { "key": "b32d0d53dd3cbdff6a2b28f951d563c72add3b459819922a00ce610d746f8ffa" } } ], "extra": [ 1, 88, 234, 221, 93, 225, 46, 70, 215, 24, 249, 2, 18, 29, 61, 204, 204, 193, 44, 212, 14, 247, 173, 46, 247, 34, 222, 25, 181, 65, 141, 233, 215, 2, 17, 0, 0, 0, 5, 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