Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 705809c71775d151a45be50018a7dfba12141a86bc247c02f8818160e23e63f2

Tx prefix hash: b83c4e32460525eb0a819033785a7afbac4330d23751b0e1a71dd59bdd41f7aa
Tx public key: fe16e5cc553c64b902c30e4fe3e32a70ed7bdc9915d69f9da0df947a9ae35dce
Timestamp: 1732675488 Timestamp [UCT]: 2024-11-27 02:44:48 Age [y:d:h:m:s]: 00:155:14:39:36
Block: 1162537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111046 RingCT/type: yes/0
Extra: 01fe16e5cc553c64b902c30e4fe3e32a70ed7bdc9915d69f9da0df947a9ae35dce0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38d6610126cf535f605c135efed5c1ebab1ea5e38a82e3eab43325018ee78988 0.600000000000 1648194 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": 1162547, "vin": [ { "gen": { "height": 1162537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38d6610126cf535f605c135efed5c1ebab1ea5e38a82e3eab43325018ee78988" } } ], "extra": [ 1, 254, 22, 229, 204, 85, 60, 100, 185, 2, 195, 14, 79, 227, 227, 42, 112, 237, 123, 220, 153, 21, 214, 159, 157, 160, 223, 148, 122, 154, 227, 93, 206, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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