Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9780973541aa4334ff912661efc9b7d5798f2a949a307b4fcd44adf70406b1c

Tx prefix hash: 2d852a9ef2413e539db1b6d3733c29637455233850e5339e69f123c0bcf080e4
Tx public key: e264dce296d6e687df376b04acbbf428e3d1a6df2d556c036c561a608594a267
Timestamp: 1697302436 Timestamp [UCT]: 2023-10-14 16:53:56 Age [y:d:h:m:s]: 01:109:19:48:19
Block: 869579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339495 RingCT/type: yes/0
Extra: 01e264dce296d6e687df376b04acbbf428e3d1a6df2d556c036c561a608594a26702110000000533af99f4000000000000000000

1 output(s) for total of 0.806721853000 dcy

stealth address amount amount idx
00: 93163baa77ef53dfc459d1acb0f7a9bec18aa1e82395fb22f9598ff6baf0f5a4 0.806721853000 1324428 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": 869589, "vin": [ { "gen": { "height": 869579 } } ], "vout": [ { "amount": 806721853, "target": { "key": "93163baa77ef53dfc459d1acb0f7a9bec18aa1e82395fb22f9598ff6baf0f5a4" } } ], "extra": [ 1, 226, 100, 220, 226, 150, 214, 230, 135, 223, 55, 107, 4, 172, 187, 244, 40, 227, 209, 166, 223, 45, 85, 108, 3, 108, 86, 26, 96, 133, 148, 162, 103, 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