Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 635d15faf55869f1c34428b31defb99cc847c0934979d7f27dd936f5470b5a06

Tx prefix hash: 60e92e8c6de55f3a7474b81cad2002892b43560117df0e2aa7a88a281a473271
Tx public key: bc1d7fcc9027c0d9b93447c85f9863cfca43180c8b6fc68f4674e88c3c7981c8
Timestamp: 1700352755 Timestamp [UCT]: 2023-11-19 00:12:35 Age [y:d:h:m:s]: 01:140:18:55:57
Block: 894670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361787 RingCT/type: yes/0
Extra: 01bc1d7fcc9027c0d9b93447c85f9863cfca43180c8b6fc68f4674e88c3c7981c8021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.666172784000 dcy

stealth address amount amount idx
00: fd4efd29c6cbfcb1997b767fb4ecc5a4c348aa56f080308511607620f03beaf5 0.666172784000 1350877 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": 894680, "vin": [ { "gen": { "height": 894670 } } ], "vout": [ { "amount": 666172784, "target": { "key": "fd4efd29c6cbfcb1997b767fb4ecc5a4c348aa56f080308511607620f03beaf5" } } ], "extra": [ 1, 188, 29, 127, 204, 144, 39, 192, 217, 185, 52, 71, 200, 95, 152, 99, 207, 202, 67, 24, 12, 139, 111, 198, 143, 70, 116, 232, 140, 60, 121, 129, 200, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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