Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0549f79d2ae951f2cef6f0fcbfcd91b42007a04b22011f8ac6a7d89d94cc18db

Tx prefix hash: e56252784e99618c45522f86f17a52ba0857c21d0c90befc8d50214fd29c4fb8
Tx public key: 9e9b8a4f7604ca43a876afe853ef668fbde6dff7535f14f77872b6be29e6424b
Timestamp: 1693990907 Timestamp [UCT]: 2023-09-06 09:01:47 Age [y:d:h:m:s]: 01:195:01:59:27
Block: 842104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400557 RingCT/type: yes/0
Extra: 019e9b8a4f7604ca43a876afe853ef668fbde6dff7535f14f77872b6be29e6424b02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.994855356000 dcy

stealth address amount amount idx
00: c9fd499cf51073b5bf732c1573feda6cdd504a14bbcd0bb2eee54b4e5f7e8209 0.994855356000 1295196 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": 842114, "vin": [ { "gen": { "height": 842104 } } ], "vout": [ { "amount": 994855356, "target": { "key": "c9fd499cf51073b5bf732c1573feda6cdd504a14bbcd0bb2eee54b4e5f7e8209" } } ], "extra": [ 1, 158, 155, 138, 79, 118, 4, 202, 67, 168, 118, 175, 232, 83, 239, 102, 143, 189, 230, 223, 247, 83, 95, 20, 247, 120, 114, 182, 190, 41, 230, 66, 75, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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