Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4c4c58bb9a2b138447fb81f2d0c2b20c080b3caca6fac1173478dcaaa27de2e

Tx prefix hash: 12b0c6f0423a3db52f234544e54fdf564340c553e41ff52eba23ba701eb90baa
Tx public key: 1aa83e6942f0d857e8ea7f83003dcf779ac986ad4772dc4f12466eac8fadd4ce
Timestamp: 1714603094 Timestamp [UCT]: 2024-05-01 22:38:14 Age [y:d:h:m:s]: 01:047:08:33:51
Block: 1012815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294680 RingCT/type: yes/0
Extra: 011aa83e6942f0d857e8ea7f83003dcf779ac986ad4772dc4f12466eac8fadd4ce02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7137478ef1a1624c67f11da2068d725245f9f4013fcdc20549e556b2a45a49b5 0.600000000000 1475456 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": 1012825, "vin": [ { "gen": { "height": 1012815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7137478ef1a1624c67f11da2068d725245f9f4013fcdc20549e556b2a45a49b5" } } ], "extra": [ 1, 26, 168, 62, 105, 66, 240, 216, 87, 232, 234, 127, 131, 0, 61, 207, 119, 154, 201, 134, 173, 71, 114, 220, 79, 18, 70, 110, 172, 143, 173, 212, 206, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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