Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f74cd0c4b0ab0cef67e7d7786bae7e389f98789b641debc0a53a0b833f51950e

Tx prefix hash: 23aa2993a5fc38c9e4c6965022d818d42232dac0655fa96b423f0e5900462c62
Tx public key: fa438132230d91fd10b6d95430a526e88b44d64da3e4d12746e8a9e314d39b0d
Timestamp: 1692391239 Timestamp [UCT]: 2023-08-18 20:40:39 Age [y:d:h:m:s]: 01:263:01:46:18
Block: 828839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449186 RingCT/type: yes/0
Extra: 01fa438132230d91fd10b6d95430a526e88b44d64da3e4d12746e8a9e314d39b0d02110000000275e3f0e9000000000000000000

1 output(s) for total of 1.100810119000 dcy

stealth address amount amount idx
00: 56d4dd876da35a08f76c5ffadfccf8fb073e7a5235286f3b2d627129ec1b813e 1.100810119000 1281189 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": 828849, "vin": [ { "gen": { "height": 828839 } } ], "vout": [ { "amount": 1100810119, "target": { "key": "56d4dd876da35a08f76c5ffadfccf8fb073e7a5235286f3b2d627129ec1b813e" } } ], "extra": [ 1, 250, 67, 129, 50, 35, 13, 145, 253, 16, 182, 217, 84, 48, 165, 38, 232, 139, 68, 214, 77, 163, 228, 209, 39, 70, 232, 169, 227, 20, 211, 155, 13, 2, 17, 0, 0, 0, 2, 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