Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77f653b8aadca68245bd03f78f5a46d55515b12914e40f99390b1cc51db6614e

Tx prefix hash: dd68c1123ab045801460d842fb75f092cf892e3f9e115f3806d83fb14ec6e457
Tx public key: 939610ef9367f171c629bf7af16cd1e2df6efad1fa4ddd0166e4da8cfaaf146f
Timestamp: 1699724990 Timestamp [UCT]: 2023-11-11 17:49:50 Age [y:d:h:m:s]: 01:106:18:38:54
Block: 889463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337469 RingCT/type: yes/0
Extra: 01939610ef9367f171c629bf7af16cd1e2df6efad1fa4ddd0166e4da8cfaaf146f02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.693170140000 dcy

stealth address amount amount idx
00: e7a0a69108e40f5c0d341f42c00f198b9afd56ffa647d00b6a29ef388f4bad47 0.693170140000 1345460 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": 889473, "vin": [ { "gen": { "height": 889463 } } ], "vout": [ { "amount": 693170140, "target": { "key": "e7a0a69108e40f5c0d341f42c00f198b9afd56ffa647d00b6a29ef388f4bad47" } } ], "extra": [ 1, 147, 150, 16, 239, 147, 103, 241, 113, 198, 41, 191, 122, 241, 108, 209, 226, 223, 110, 250, 209, 250, 77, 221, 1, 102, 228, 218, 140, 250, 175, 20, 111, 2, 17, 0, 0, 0, 1, 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