Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 494a8fa28329ef1929915b20275f2a1929191558d654e80a9dabf47c1a7dc774

Tx prefix hash: 65a3e5da73187dfb759b0e7e63714566c3a5f06c6020b33d650143777e5b46cc
Tx public key: 765b37a9ea8bb83b9000fadf3a5abf1c9b1015d7b41d6c743fe6d48c13cddcc5
Timestamp: 1700970758 Timestamp [UCT]: 2023-11-26 03:52:38 Age [y:d:h:m:s]: 01:159:11:06:40
Block: 899788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375148 RingCT/type: yes/0
Extra: 01765b37a9ea8bb83b9000fadf3a5abf1c9b1015d7b41d6c743fe6d48c13cddcc502110000000233af99f4000000000000000000

1 output(s) for total of 0.640661786000 dcy

stealth address amount amount idx
00: 2d6c3ab9c85d6f26d0e37567863a5222cb4a37f86df4c408e7d8acabbe52c476 0.640661786000 1356251 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": 899798, "vin": [ { "gen": { "height": 899788 } } ], "vout": [ { "amount": 640661786, "target": { "key": "2d6c3ab9c85d6f26d0e37567863a5222cb4a37f86df4c408e7d8acabbe52c476" } } ], "extra": [ 1, 118, 91, 55, 169, 234, 139, 184, 59, 144, 0, 250, 223, 58, 90, 191, 28, 155, 16, 21, 215, 180, 29, 108, 116, 63, 230, 212, 140, 19, 205, 220, 197, 2, 17, 0, 0, 0, 2, 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