Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6179629ce0a6b0bc62569e549f3c490b7a88d92e85d66a9db78eedf8986c9501

Tx prefix hash: eba13f31708b49307b20affd3d824f609e2fae2b3a7a57ab80f4c0519f3f1353
Tx public key: 303316769a82d4df3479002821945938b28f1b0c8f3ec7d788cef8b1cc427a99
Timestamp: 1720486468 Timestamp [UCT]: 2024-07-09 00:54:28 Age [y:d:h:m:s]: 00:269:01:03:15
Block: 1061596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192204 RingCT/type: yes/0
Extra: 01303316769a82d4df3479002821945938b28f1b0c8f3ec7d788cef8b1cc427a9902110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c38ee191dbc9b79a03f7ab630306a783dd69c09397bd3a98d0c1f43226e85b28 0.600000000000 1532087 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": 1061606, "vin": [ { "gen": { "height": 1061596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c38ee191dbc9b79a03f7ab630306a783dd69c09397bd3a98d0c1f43226e85b28" } } ], "extra": [ 1, 48, 51, 22, 118, 154, 130, 212, 223, 52, 121, 0, 40, 33, 148, 89, 56, 178, 143, 27, 12, 143, 62, 199, 215, 136, 206, 248, 177, 204, 66, 122, 153, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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