Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 750911d94fbedf0b35342352e67a3287878fc2d9c8116c645f882766a7a59d07

Tx prefix hash: 60ddd2d161d267f223cf206599a1cdffdf16d4cb2245717af462123549ce8481
Tx public key: 2e8bc2e78bf81d3e802fbe612ae30b785ade4bca90916cfdac519ed644cc83a3
Timestamp: 1675099270 Timestamp [UCT]: 2023-01-30 17:21:10 Age [y:d:h:m:s]: 01:354:06:32:21
Block: 686177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514153 RingCT/type: yes/0
Extra: 012e8bc2e78bf81d3e802fbe612ae30b785ade4bca90916cfdac519ed644cc83a302110000000133af99f4000000000000000000

1 output(s) for total of 3.268968133000 dcy

stealth address amount amount idx
00: ed7b6d93c6d3e5a0924c6dbc0009180d7a727cccc7190a7a60a26100037fb874 3.268968133000 1128648 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": 686187, "vin": [ { "gen": { "height": 686177 } } ], "vout": [ { "amount": 3268968133, "target": { "key": "ed7b6d93c6d3e5a0924c6dbc0009180d7a727cccc7190a7a60a26100037fb874" } } ], "extra": [ 1, 46, 139, 194, 231, 139, 248, 29, 62, 128, 47, 190, 97, 42, 227, 11, 120, 90, 222, 75, 202, 144, 145, 108, 253, 172, 81, 158, 214, 68, 204, 131, 163, 2, 17, 0, 0, 0, 1, 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